-
Notifications
You must be signed in to change notification settings - Fork 75
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: rewrite to use Deno FFI #99
Conversation
One final blocker denoland/deno#13162 |
might want to update the README to disclose that you got rid of the need for https://github.com/webview/webview_deno#deno https://github.com/denosaurs/plug |
@brandonros Plug will still be needed for this pr as to allow for versioned caching of dylibs and easy loading from urls. |
@eliassjogreen Callback support in Deno FFI is blocked on rusty_v8's Locker API. I had a small discussion internally and we (Deno) are not so sure about the concept of Rust calling into V8. To unblock deno_webview, maybe we should just do a wrapper to the callbacks? This increases maintenance but was already the case with plugins. WDYT? |
Sure, that sounds like a good idea until callback support is added. |
Sorry for going a bit off-topic but I just wanted to say I added a small bounty for issue #96 (which should be closed by this PR) to express my excitement and gratefulness. Thanks for the work y'all put in so far. I would try to help if I had any knowledge of rust or this FFI stuff. 😝 |
Could you also update the version tag in |
you might want to delete the empty .gitmodules leftover file |
@eliassjogreen anything left review wise? |
Running the README example: import { Webview } from "https://deno.land/x/webview/mod.ts";
const html = `
<html>
<body>
<h1>Hello from deno v${Deno.version.deno}</h1>
</body>
</html>
`;
const webview = new Webview();
webview.navigate(`data:text/html,${encodeURIComponent(html)}`);
webview.run();
Not sure if you need to release? Edit: needed deno v1.18.0 |
Strange i am not getting the same error when running locally, have you tried the |
Breaking Changes
notblock the JS event loop but spawning multiple webviews (one at a time) is still possible. This is a design limitation. One solution to this is native support for FFI callbacks (WIP)setTitle
changes to a setter onwebview.title
. Same forsetSize
cc @eliassjogreen
Closes #96
Closes #98
Closes #94
Closes #6
Closes #76
Closes #89
Closes #79